Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces several updates to the Dev Pack for Salesforce extension, focusing on improving documentation, updating dependencies, and streamlining the codebase by removing unused commands and files. The most notable changes include enhancements to the
README.md, addition of new recommended extensions, updates to the linting configuration, and significant cleanup of obsolete command implementations.Documentation and Extension Updates:
README.mddetailing auto-configuration, Apex log management, metadata refresh, and environment health check capabilities.SF PreflightandSF Metadata Trackeras recommended extensions in both theREADME.mdand thepackage.jsonextension list. [1] [2]Codebase Simplification and Cleanup:
BetterComments.js,EnvironmentHealth.js,ForceCheckPackages.js,NodePackageManager.js, and their associated commands/configuration frompackage.json. This streamlines the extension and removes unnecessary maintenance overhead. [1] [2] [3] [4] [5] [6] [7] [8]Tooling and Configuration Improvements:
eslint.config.jsfile using the latest ESLint configuration syntax and updatedpackage.jsonto support ECMAScript modules (type: "module"), ensuring modern linting and compatibility. [1] [2]Version and Script Updates:
2.1.0and made minor improvements to script messages inpackage.json.Documentation Cleanup:
README.mddescribing automatic npm package detection and installation, as this feature has been deprecated.These changes collectively modernize the extension, improve the onboarding experience, and reduce technical debt.